220-1202: Core 2 Practice Exam — 220-1202: Core 2

" target="_blank" rel="nofollow noopener">https://img.examtopics.com/220-1202/image23.png">

The scenario requires cross-platform remote access between a Windows client and legacy Linux system, with the ability to view the user's active session and interact with it in real time. For the CompTIA 220-1202 (A+ Core 2) exam, candidates are expected to match remote access tools to use cases based on compatibility, functionality, and deployment requirements. VNC meets all the stated requirements: it is platform-agnostic, natively supports screen sharing of the active user session, has existed for decades making it compatible with legacy Linux distributions, and has Windows client support to allow the technician to connect and interact with the remote Linux desktop session directly. Option Analysis: A. Incorrect. A VPN only establishes a secure encrypted network connection between the technician's laptop and the remote network. It does not provide any native screen sharing, session visibility, or interactive control functionality for the remote user's desktop, so it cannot fulfill the core requirements of the use case. B. Correct. VNC is cross-platform, supports direct access to the active user's graphical desktop session, is compatible with legacy Linux systems due to its long development history, and has readily available Windows clients that support viewing and interacting with remote Linux sessions. It fully addresses every requirement in the scenario. C. Incorrect. SSH is primarily a command-line remote access protocol for Linux systems. While it supports X11 forwarding to run individual graphical applications, it does not provide access to the existing active user's full desktop session by default, so the technician cannot view what the end user is currently doing, which fails a key requirement of the scenario. D. Incorrect. RDP is Microsoft's proprietary remote desktop protocol, primarily designed for Windows systems. While third-party RDP servers exist for modern Linux distributions, they are rarely natively supported on legacy Linux deployments. Additionally, RDP defaults to creating a new, separate desktop session rather than connecting to the existing active user session, so it does not allow the technician to view the user's current activity as required. Key Concepts: 1. Remote Access Tool Use Case Matching: A core 220-1202 competency that requires candidates to select the appropriate remote tool based on platform compatibility, required functionality (screen sharing, command line, session access), and system age to meet support requirements. 2. Cross-Platform Remote Desktop Protocols: Candidates must differentiate between proprietary protocols like RDP and open, platform-agnostic protocols like VNC, and understand which are suitable for mixed Windows/Linux support scenarios. 3. Active vs. Independent Remote Sessions: The 220-1202 exam tests knowledge of which tools connect to a user's existing active session for collaborative support, versus those that create a separate, independent session for administrative access. References: CompTIA A+ Core 2 (220-1202) Exam Objectives, RealVNC Official VNC Overview Documentation

This question aligns with the CompTIA 220-1202 (A+ Core 2) domain 3: Operating Systems, specifically Windows client networking and Active Directory domain join troubleshooting. The scenario confirms full IP layer connectivity is functional: the technician can ping the domain server (typically via IP address) and access the public internet, so issues with IP assignment, subnet configuration, or gateway routing are eliminated. Joining a Windows workstation to an Active Directory domain requires the client to resolve special SRV (Service Location) resource records that identify domain controllers for the target domain. These records are exclusively hosted on internal, AD-integrated DNS servers. The most common cause of a "domain cannot be found" error with working IP connectivity is the workstation being configured to use public DNS servers (such as those from an ISP or public providers like Google DNS) instead of the internal AD DNS server. Changing the DNS settings to point to the correct internal AD DNS server resolves the name resolution barrier to domain join. Option Analysis: A. Correct. Domain join operations depend entirely on DNS to locate Active Directory domain controllers via AD-specific SRV records. If the workstation’s DNS is pointed to a non-AD DNS server (e.g., public DNS), it cannot resolve the records required to find the domain, even with working IP connectivity. Updating the DNS settings to use the internal AD-integrated DNS server fixes this issue. B. Incorrect. The workstation already has valid IP connectivity, as confirmed by successful pings to the server and internet access, whether it received an IP via DHCP or is configured statically. The IP assignment method is not the root cause of the domain lookup failure. C. Incorrect. A misconfigured subnet mask would prevent communication with devices outside the local subnet, which would block internet access and cross-subnet pings to the server. Since both of these functions work, the subnet mask is correctly configured and not the issue. D. Incorrect. The default gateway is responsible for routing traffic to remote subnets and the public internet. Since internet access works, the default gateway is properly configured and not the source of the domain lookup error. Key Concepts: 1. Active Directory Domain Join Prerequisites: As covered in the 220-1202 exam objectives, Windows domain join requires the client to resolve AD-specific DNS records to locate domain controllers, making correct DNS configuration a non-negotiable requirement for successful domain joins. 2. DNS Role in Active Directory: AD-integrated DNS servers host unique SRV and A records for domain services that are not present on public DNS servers. Using public DNS for a workstation on an AD network will block access to internal domain resources even if general internet connectivity works. 3. OS Layer Network Troubleshooting: The 220-1202 exam emphasizes distinguishing between layer 3 (IP connectivity) issues and layer 7 (name resolution/service access) issues by testing connectivity via IP vs. hostname when diagnosing network errors. References: Troubleshoot domain join errors, CompTIA A+ 220-1202 Exam Objectives

This question assesses knowledge of change management processes, a core component of the IT Operational Procedures domain for the CompTIA 220-1202 (A+ Core 2) certification. The standard formal change management workflow requires that after identifying a valid need for an organizational IT change (in this case, replacing end-of-life network switches that no longer receive vendor support or security updates), the first required action is to formally submit a change proposal to the relevant change control body. This proposal documents the business case, expected costs, risk level, impact to operations, and preliminary rollback plan for stakeholder review before any subsequent steps are taken. The suggested answer C aligns with this required first step in the formal change control process outlined in the 220-1202 exam objectives. Option Analysis: A. Implement the change: Incorrect. Implementation is a late-stage change management activity that only occurs after the change has been formally proposed, reviewed, approved, scheduled, and communicated to all affected stakeholders. Unauthorized implementation without prior review violates IT change control policies, introduces unassessed risk of network outages, unbudgeted costs, and unplanned business disruption. B. Approve the change: Incorrect. Change approval is the responsibility of a designated change authority, such as a Change Advisory Board (CAB) or IT management, not the technician who identified the need for the change. Approval also only occurs after a formal change proposal has been submitted and fully reviewed for risk, cost, and operational impact, so this is not a valid first step for the technician. C. Propose the change: Correct. Per the 220-1202 certification's defined change management framework, the first action for a technician who identifies a required IT change is to formally propose the change to the appropriate change control body. This proposal initiates the formal review process to ensure the change is justified, low-risk, and aligned with business priorities before any further action is taken. D. Schedule the change: Incorrect. Scheduling of a change only takes place after the change has received formal approval from the relevant change authority. Scheduling cannot occur before the change is reviewed and approved, as the change may be rejected, modified, or assigned a different priority by the change control body, so this is a later step in the workflow. Key Concepts: 1. Change Management Workflow (220-1202 IT Operational Procedures): The formal sequence for IT changes is identify need, submit change proposal, review/approve change, schedule change, notify stakeholders, implement change, document post-implementation results. Following this sequence minimizes operational risk and ensures alignment with business goals. 2. End-of-Life (EOL) Hardware Risk: EOL network hardware no longer receives vendor firmware updates, security patches, or technical support, creating significant security vulnerabilities and operational risk that qualifies as a valid trigger for a formal change request. 3. Change Control Role Segregation: Per 220-1202 best practices, technicians who identify needed changes are responsible for submitting change proposals, but do not have the authority to approve their own requests, ensuring independent review of all proposed changes for potential risk. References: CompTIA A+ 220-1202 Exam Objectives, CompTIA IT Change Management Best Practices Guide

The scenario describes MFA failure for a custom web application on a smartphone immediately after international travel. Per CompTIA 220-1202 (A+ 12th Edition) software and troubleshooting domains, the first step in resolving end-user issues is to identify the most probable, low-effort root cause before implementing disruptive or advanced fixes. The vast majority of software MFA implementations use the Time-based One-Time Password (TOTP) protocol, which requires the client device (smartphone) and the backend authentication server to have closely synchronized time (within a 30 to 90 second window) to generate matching valid access codes. International travel frequently leads to misconfigured time, time zone, or date settings, either if the user has disabled auto-time sync, or the device fails to update time settings while roaming in a new country. This makes verifying date and time settings the logical first troubleshooting action, as it resolves the most common cause of post-travel MFA failure with no disruption to user data or device configuration. Option Analysis: A. Correct. TOTP-based MFA relies on time synchronization between the client device and authentication server. International travel is a common trigger for time/date misconfiguration if the device does not automatically update time zone or sync with network time servers while roaming. Verifying date and time settings is a non-invasive, high-probability first step that aligns with CompTIA A+ troubleshooting best practices. B. Incorrect. Applying mobile OS patches addresses known software bugs and security vulnerabilities, but there is no evidence in the scenario that an outdated OS is the cause of the MFA failure. The issue is tied directly to international travel, so OS patching is not a relevant first step, and it is a more disruptive action that should only be performed after simpler root causes are ruled out. C. Incorrect. Uninstalling and reinstalling the MFA application erases local app configuration and requires the user to re-enroll their MFA token, which is a highly disruptive step. There is no indication of app corruption in the scenario, so this action is not appropriate as a first troubleshooting step and would only be considered after simpler checks like date/time verification are completed. D. Incorrect. Escalation to the website developer is a last resort step that is only performed after all client-side troubleshooting steps have been exhausted and the root cause is confirmed to be on the application backend. The scenario indicates the issue is isolated to a single user post-travel, so client-side troubleshooting must be completed first, making escalation an incorrect first action. Key Concepts: 1. CompTIA A+ Troubleshooting Methodology: Core 2 (220-1202) domain 4 emphasizes following a structured troubleshooting process that prioritizes least invasive, highest probability fixes first to minimize user disruption and resolve issues efficiently. 2. Time-based One-Time Password (TOTP) Operation: TOTP is the dominant standard for software MFA, and its functionality is entirely dependent on synchronized time between the client device and authentication server. Even small time mismatches greater than 90 seconds will prevent valid MFA code generation. 3. Mobile Device Time Configuration: Mobile devices rely on either cellular network time or NTP (Network Time Protocol) sync to maintain accurate date, time, and time zone settings. Roaming internationally can disrupt this sync if auto-time settings are disabled or the device cannot connect to local time servers, leading to configuration mismatches. References: CompTIA A+ 220-1202 Exam Objectives, NIST Special Publication 800-63B: Digital Identity Guidelines - Authentication and Lifecycle Management, https://pages.nist.gov/800-63-3/sp800-63b.html#sec5